Compare Page

Data maintenance

Characteristic Name: Data maintenance
Dimension: Availability and Accessability
Description: Data should be accessible to perform necessary updates and maintenance operations in it’s entirely
Granularity: Record
Implementation Type: Process-based approach
Characteristic Type: Usage

Verification Metric:

The number of tasks failed or under performed due to lack of data maintenance
The number of complaints received due to lack of continuity in data access

GuidelinesExamplesDefinitons

The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation

Guidelines: Scenario:
Technological changes in the infrastructure/system should be handled in such a way that they should not make data inaccessible (1) Sales order is created once a customer signs a contract. Then it is updated in three instances 1)Delivery date and shipment date is updated once the production plan is created. 2) Actual quantity is updated once the manufacturing is complete 3) Total cost is updated once the freight changes are incurred. A sales order is achieved after one years from delivery.
A maintenance policy for mission critical data should be developed and implemented to handle on going systematic updates (Create, read, update, delete, archive and cleanse) (1) Customer data : Created when a customer enters into a contract, updated once the customer details change or contact change, archived once the contact end
When multiple versions of the same data is available through different datasets\databases create a master record and make it available across the systems (1) Master data management
Leverage application and storage technology in such a way that the maintenance policies can be applied on data (1)Addresses which were not updated during the last 24 months are prompted for validations
Create a responsibility structure/Authorisation structure and a communication structure to manage the process of information generation maintenance and utilisation (1) It is the responsibility of the work study team to provide SMV (standard minute values) for a garment.
(2) Approved SMVs should be sent to the planning department for planning purposes.

Validation Metric:

How mature is the data maintenance process

These are examples of how the characteristic might occur in a database.

Example: Source:
minutes of a meeting will be produced in draft form and reviewed by the members of the committee before being approved. Once this process of creation is finished the record must be fixed and must not be susceptible to change. If a record is changed or manipulated in some way, it no longer provides evidence of the transaction it originally documented. For example, if someone alters the minutes of a meeting after they have been approved, the minutes can no longer be considered an accurate record of the meeting. This is another issue that becomes more important in an electronic context. K. Smith, “Public Sector Records Management: A Practical Guide”, Ashgate, 2007.

The Definitions are examples of the characteristic that appear in the sources provided.

Definition: Source:
A measure of the degree to which data can be accessed and used and the degree to which data can be updated, maintained, and managed. D. McGilvray, “Executing Data Quality Projects: Ten Steps to Quality Data and Trusted Information”, Morgan Kaufmann Publishers, 2008.
Can all of the information be organized and updated on an on-going basis? EPPLER, M. J. 2006. Managing information quality: increasing the value of information in knowledge-intensive products and processes, Springer.

 

Redundancy

Characteristic Name: Redundancy
Dimension: Consistency
Description: The data is recorded in exactly one place
Granularity: Record
Implementation Type: Rule-based approach
Characteristic Type: Declarative

Verification Metric:

The volume of redundant data as a percentage to total data

GuidelinesExamplesDefinitons

The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation

Guidelines: Scenario:
Maintain the database schema eliminating the causes for redundancies of entities and attributes (1) All customers are in customer table
Ensure that there are no redundant records across distributed databases (1) Organisation has different customer bases maintained in different databases. But one customer is available only in one database
Ensure that same entity is not originally captured more than once in the systems (1) Medical Insurance system refers employee bank details from the payroll.
Ensure that there are no temporary table backups are available in the database (1) Created a backup for employees as employee_temp for a specific purpose and it is still in the database

Validation Metric:

How mature is the creation and implementation of the DQ rules to eliminate the occurrence of redundant data

These are examples of how the characteristic might occur in a database.

Example: Source:
A school has 120 current students and 380 former students (i.e. 500 in total) however; the Student database shows 520 different student records. This could include Fred Smith and Freddy Smith as separate records, despite there only being one student at the school named Fred Smith. This indicates a uniqueness of 500/520 x 100 = 96.2% N. Askham, et al., “The Six Primary Dimensions for Data Quality Assessment: Defining Data Quality Dimensions”, DAMA UK Working Group, 2013.

The Definitions are examples of the characteristic that appear in the sources provided.

Definition: Source:
A measure of unwanted duplication existing within or across systems for a particular field, record, or data set. D. McGilvray, “Executing Data Quality Projects: Ten Steps to Quality Data and Trusted Information”, Morgan Kaufmann Publishers, 2008.
There is only one record in a given data store that represents a Single Real-World Object or Event. ENGLISH, L. P. 2009. Information quality applied: Best practices for improving business information, processes and systems, Wiley Publishing.
Determines the extent to which the columns are not repeated. G. GATLING, C. B., R. CHAMPLIN, H. STEFANI, G. WEIGEL 2007. Enterprise Information Management with SAP, Boston, Galileo Press Inc.